Backup power supply support

ABSTRACT

Example implementations relate to backup power supply support. For example, a backup power supply support system can include a shared backup power supply controlled by a backup power control module and a support switch coupled to the shared backup power supply. The support switch enables a transition from a primary power supply to the shared backup power supply and the support switch includes system firmware. The system firmware detects a primary power supply compromise, isolates a hardware switch from the shared backup power supply, enables the hardware switch, and transitions to the shared backup power supply.

BACKGROUND

As reliance on computing systems continues to grow, so too does thedemand for reliable power systems and back-up schemes for thesecomputing systems. Servers, for example, may provide architectures forbacking up data to flash or persistent memory as well as back-up powersources for powering this back-up of data after the loss of power.Backup power supplies may sometimes include energy components such ascapacitors or batteries.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an example of a backup powersupply support system, according to the present disclosure;

FIG. 2 illustrates an example of a system for backup power supplysupport, according to the present disclosure;

FIG. 3 illustrates a flow diagram of an example of a process of backuppower supply support, according to the present disclosure; and

FIG. 4 illustrates a flow diagram of an example of a method of backuppower supply support, according to the present disclosure.

DETAILED DESCRIPTION

A computing data storage system can include a number of nodes thatsupport a number of loads. The nodes can be a number of servers, forexample. A number of loads can include storage controllers or devicesassociated with the servers. For example, a load can include cachememory, dual inline memory modules (DIMMs), Non-Volatile Dual In-LineMemory Modules (NVDIMMs), and/or smart array control logic, controllogic (e.g., Asynchronous DRAM Refresh (ADR) logic), among other storagecontrollers and/or devices associated with the servers. A computing datastorage system can include a backup power system operatively coupled tothe number of nodes to support the number of loads in an event of aremoval of a primary power supply.

A removal of a primary power supply can be scheduled or un-scheduled.For instance, a scheduled removal of the primary power supply can be theresult of scheduled maintenance on the number of nodes and/or the numberof loads. A scheduled removal of the primary power supply can be anintentional power down of the number of nodes and/or the number of loadsto add and/or remove nodes to a chassis and/or network connected to aprimary power supply. In another example, a scheduled removal of theprimary power supply can be an intentional power down to add and/orremove one or more loads to or from one or more nodes.

An un-scheduled primary power supply removal can be a failure in theprimary power supply. An un-scheduled primary power supply removal canoccur when, for example, the primary power supply fails momentarilyand/or for an extended period of time. Failure can include anunintentional loss of power to nodes and/or loads from the primary powersupply.

It may be desirable to move data from cache memory in the number ofnodes to non-volatile memory upon the removal of a primary power supply.However, moving data from cache memory to non-volatile memory caninvolve a power supply. A backup power supply can be a secondary powersupply that is used to provide power for moving data from cache memoryto non-volatile memory when the primary power is removed.

In accordance with examples of the present disclosure, a backup powersupply support system can enable and/or disable hardware switchcircuitry to prevent power surge problems. Enabling and/or disabling thehardware switch circuitry can prevent damage to the motherboard when adesign flaw and/or power surge may be present. As used herein, enablinga hardware switch refers to the hardware switch remaining operableand/or functioning as designed. Alternatively, disabling the hardwareswitch can refer to the hardware switch remaining off, non-enabled,and/or not functioning to transition.

FIG. 1 illustrates a block diagram of an example of a backup powersupply support system 100, according to the present disclosure. Asillustrated in FIG. 1, the system 100 can include a shared backup powersupply 110 controlled by a backup power control module 106, and asupport switch 105 coupled via a link 118 to a hardware switch 103. Thelink 118 can include a physical link.

The support switch 105 can enable a transition from a primary powersupply 109 to the shared backup power supply 110. The support switch 105can include system firmware to detect a primary power supply 109compromise and to isolate the hardware switch 103. As used herein, thesupport switch is instructions that can be executed by a processingresource to turn on and/or shut off a device in a particular situation.For example, the instructions can be executed to perform an emergencystop safety mechanism, and/or proceed with a transition as discussedfurther herein. Further, in some examples, the support switch can beexecuted to (completely and quickly) abort an operation and/or instructthe execution of operations.

As used herein, the hardware switch 103 is an electrical component thatcan break an electrical circuit, interrupting the current or divertingit. For example, a hardware switch can be a switch-mode power supplytype of transformer. The hardware switch can be connected to the primarypower supply 109, the shared backup power supply 110, and sub-module 108that is associated with the node 122. The hardware switch 103 can becoupled to the sub-module 108 via link 114. The support switch 105 cancommunicate with the hardware switch 103 via the link 118.

The system firmware of support switch 105 can enable and/or disable thehardware switch 103 and transition power provided to the node 122, fromthe primary power supply 110 to the shared backup power supply 110. Asused herein, transition refers to the change of power supplied to a node122, transitioning from the primary power supply 109 to power suppliedfrom the shared backup power supply 110 to the node 122.

The shared backup power supply 110 and the backup power control module106 can be coupled to a sub-module 104 via connection 124. The sharedbackup power supply 110 can be coupled via link 118 to the hardwareswitch 103. The hardware switch 103 can be coupled via link 114 tosub-module 108. The shared backup power supply 110 can be controlled bythe backup power control module 106, as discussed further in relation toFIGS. 2 and 3.

Similarly, the primary power supply 109 can be controlled by a mainpower module (not illustrated). The primary power supply 109 and themain power module can be coupled by link 107 to the hardware switch 103.The primary power supply 109 and the main power module can be coupled bylink 111 to the sub-module 104 on the node 122.

Also, as illustrated in FIG. 1, the node 122 can include a plurality ofsub-modules 104, 108. The node 122 can support a plurality of loads(e.g., load 160-1, load 160-2, load 160-3, and load 160-4, collectivelyreferred to herein as loads 160). For instance, the node 122 can supportplurality of sub-modules 104, 108 that can include a number of storagecontrollers and/or a number of storage devices such as NVDIMMs. In someexamples, a hardware switch can be embedded in a load (not illustratedin FIG. 1). For instance, a separate hardware switch can be embedded ineach of load among the plurality of loads 160-1 and 160-2.

The node 122 can include a Baseboard Management Controller (BMC) unitthat enables communication between the shared backup power supply 110and the sub-module 104 and the loads 160-1, 160-2. The BMC unit can be aspecialized microcontroller embedded on the motherboard of the node 122,and that manages the interface between system management software andplatform hardware. The BMC unit can be computer executable instructionsstored on the node 122. Examples of the BMC unit can include BasicInput/Output System (BIOS). BIOS provides initialization and testing ofthe hardware components of the node 122 and loads an operating systemfor the node when it is powered on. While examples herein use BIOS asexamples of a BMC unit, examples of the present disclosure are not solimited.

The system firmware of support switch 105 can enable and/or disable thehardware switch 103 and transition power provided to the sub-modules 104and 108 on node 122, from the primary power supply 110 to the sharedbackup power supply 110. The transition to the shared backup powersupply 110 can provide power to sub-modules 104, 108. For instance,loads 160-3 and 160-4 may be associated with sub-module 108 on node 122.The node and/or sub-module 108 (and by default, loads 160-3, 160-4) canreceive power from primary power supply 109 from the hardware switch 103via link 114.

The support switch 105 can receive data indicating, for example,additional power requirements for loads 160-1 and 160-2 on sub-module104. The support switch 105 can communicate with hardware switch 103 toenable a transition to backup power supply 110 to power the sub-modules104 and 108. The sub-module 104 can be powered by backup power supply110 via connection 118. The sub-module 108 can be powered by the backuppower supply 110 via the hardware switch 103 link 114.

Alternatively, for example, the support switch may receive data thatloads 160-1, 160-2 associated with sub-module 104 may not, for example,need additional power from the backup power supply 110. The primarypower supply 109 providing power to the sub-module 104 via connection111 suffices. The support switch 105, in this instance, can disable thehardware switch 103 from transitioning to backup power supply 110. Thatis, the support switch 105 can enable the hardware switch 103 totransition to backup power supply 110 when additional power supply isdesired. Alternatively, the support switch 105 can disable the hardwareswitch 103 from transitioning to backup power supply when additionalpower is not desired.

FIG. 2 illustrates an example of a system 200 for power supply support,according to the present disclosure. As illustrated by FIG. 2, thesystem 200 includes a shared backup power supply 210, a hardware switch203, a chassis/host controller 212, and the node 222.

As illustrated in FIG. 2, the node 222 can host a number of loads (e.g.,loads 260-1, 260-2, 260-3, 260-4, collectively referred to herein asloads 260). For instance, the node 222 can include a number of devices,such as local memory or data storage (herein referred to generally asmemory). The memory may contain volatile and non-volatile memory (e.g.,cache and non-volatile memory dual inline memory modules (NVDIMM)).Thus, each memory in the node 222 can contain a number of NVDIMM slots220. Each NVDIMM slot among the number of NVDIMM slots 220 can provide aload to the system 200. Node 222 can include other devices such as cachememory, DIMMs, array control logic, and storage controllers, among otherdevices associated with the node 222, and each of the devices associatedwith the node 222 can provide a load to the system 200. For instance,load 260-2 can be provided by a storage controller, whereas each NVDIMMslot among the number of NVDIMM slots 220 can provide load 260-1. Insome examples, the node 222 can also include a control logic unit (notillustrated in FIG. 2).

The shared backup power supply 210 can include a processing resource 202connected via a connection to a memory resource 208, (e.g., acomputer-readable medium (CRM), machine readable medium (MRM), database,etc.). In some examples, a memory resource (e.g., memory resource 208)may be a non-transitory storage medium, medium and/or a non-transitorymachine readable medium, where the term “non-transitory” does notencompass transitory propagating signals. The memory resource 208 caninclude a number of computing modules. Similarly, in some examples, theprimary power supply 209 can include a processing resource connected viaa connection to a memory resource (e.g., a computer-readable medium(CRM), machine readable medium (MRM), database, etc.).

The example of FIG. 2 illustrates a backup power control module 206. Asused herein, a computing module can include program code (e.g., computerexecutable instructions) hardware, firmware, and/or logic. But acomputing module at least includes instructions executable by theprocessing resource 202 (e.g., in the form of modules) to performparticular actions, tasks, and functions described in more detail hereinin reference to FIGS. 3 and 4. Instructions associated with a particularmodule (e.g., backup power control module 206) when executed by theprocessing resource 202 can also be referred to and functioncollectively as a component and/or computing engine. As used herein, anengine can include hardware firmware, logic, and/or executableinstructions. But an engine at least includes hardware (e.g., logic inthe form of an application specific integrated circuit (ASIC)) toperform particular actions, tasks and functions described in more detailherein in reference to FIGS. 3 and 4.

Engines and/or the number of modules (e.g., backup power control 206)can be sub-engines/modules of other engines/modules and/or combined toperform particular actions, tasks, and functions within a particularsystem and/or computing device. Engines and/or modules described hereincan be located in a single system and/or computing device or reside inseparate distinct locations in a distributed computing environment(e.g., cloud computing environment).

The system 200 can perform a number of functions and operations asdescribed in FIGS. 3 and 4, and include the apparatus and methods forpower supply support as described herein.

The shared backup power supply 210 can be a battery that is external tothe node 222 and external to the chassis/host controller 212 supportingthe node 222. The shared backup power supply 210 can provide power tothe node 222. The shared backup power supply 210 can support differentchassis/host controllers (not illustrated by FIG. 2) to support aplurality of nodes on different chassis.

The node 222 can include a main logic board (MLB) 228, and the MLB 228can include BMC unit 231. The BMC unit 231 can include a number ofcomponents, such as BIOS. The number of components can allow the node222 to communicate with the shared backup power supply 210 and thechassis/host controller 212. Signal and control lines can connect theshared backup power supply 210 to the chassis/host controller 212 and tothe hardware switch 203. The hardware switch can include a multiplexer(MUX). The hardware switch 203 and the chassis/host controller 212 canbe coupled to the node 222 via a signal line 216. The signal line 216can provide for the install, registering, data, and clocking of the node222 with the chassis/host controller 212.

In some examples, the control logic (not illustrated in FIG. 2) can becoupled to the node via a control signal and power line 226. Forexample, the node 222 can provide a signal to the control signal andpower line 226 and the signal lines 216 when data is to be backed up tonon-volatile memory. The control signal and power line 226 and thesignal line 216 also couple the chassis/host controller 212 to the node222 and the control logic.

The backup power control module 206 can have instructions stored in anon-transitory storage medium (e.g., memory resource) to communicatebetween the BMC unit 231 and the plurality of loads to protect theplurality of loads 260 with backup power, as discussed further inrelation to FIGS. 3 and 4. Further, as discussed in relation to FIGS. 3and 4, the backup power control module 206 can provide instructions tosupply backup power to the node 222 from the shared backup power supply210. A support switch 205 can assist with the transition from theprimary power supply 209 to the backup power supply 210. For example,the support switch 205 can protect the node 222 from an over/undercurrent and/or over/under voltage from the shared backup power supply210. As discussed further below and in relation to FIGS. 3 and 4, thesupport switch 205 can influence a hardware switch 203, such that thefunctionality of the hardware switch 203 does not engage with the system200 after a primary power supply 209 compromise.

The support switch 205 can be connected to the shared backup powersupply 210 via connection 220. A hardware switch 203 can be connected tothe primary power supply 209. The support switch 205 can enable ahardware switch 203 and/or isolate the hardware switch 203 from theshared backup power supply 210. Isolating the hardware switch 203, asused herein, refers to disabling the switch functionality.

For example, the support switch 205 can enable and/or disable thehardware switch 203 and verify adequate power current to the node 222from the shared backup power supply 210. Verifying adequate powercurrent can include determining an adequate power voltage and/or currentto the node 222 from the shared backup power supply 210. As used herein,an adequate power current refers to a level of power that is within apredetermined voltage and current standard. By determining the powercurrent from the shared backup power supply 210 to the node 222 isadequate, damage to the motherboard may be avoided. For example, a powersurge (e.g., voltage and/or current) can be circumvented by disablingthe hardware switch 203. The support switch 205 can be used to verifyadequate power to the node.

FIG. 3 illustrates a flow diagram of an example of a process 350 ofpower supply support, according to the present disclosure. Althoughillustrated in simplified form in FIG. 3, the process 350 can includefewer and/or additional actions.

At 352, the process 350 can include monitoring a primary power supply.Monitoring a primary power supply, as used herein, refers to observingand/or tracking the supply of power from a primary power supply enteringthe node. The primary power supply (e.g., primary power supply 209illustrated in FIG. 2) can maintain a power supply to a system (e.g.,node 222 as illustrated in FIG. 2, sub-modules 104, 108 as illustratedin FIG. 1) within a particular power range. That is, the primary powersupply can provide the system with an amount of power from the primarypower supply, which maintains the supply within a predetermined powerthreshold. The predetermined power threshold can be configuredautomatically by the system and/or by a user.

At 354, the process 350 can include detecting a primary power supplyloss. That is, system firmware of the support switch (e.g., 105, 205illustrated in FIGS. 1 and 2) can detect whether the primary powersupply is compromised. A compromised primary power supply refers to theprimary power supply falling outside of a predetermined power threshold.For example, the primary power supply can fall outside of thepredetermined power threshold in response a removal of a primary powersupply. As previously discussed, a removal of a primary power supply canbe a primary power supply disruption, such as a power failure or systemreset.

Additionally and/or alternatively, the primary power supply can falloutside of the predetermined threshold when the support switch (e.g.,105, 205 as illustrated in FIGS. 1 and 2) detect an additional powerrequirement from the node (e.g., 122, 222 as illustrated in FIGS. 1 and2). For example, the node may have additional loads (e.g., plurality ofloads 160, 260 as illustrated in FIGS. 1 and 2) added, which may requireadditional power. That is, the predetermined power threshold is loaddependent. The node power requirement may increase depending upon theplurality of loads connected to the node.

Further, the primary power supply can fall outside of a predeterminedpower threshold in response to the primary power supply no longer beingwithin the predetermined power threshold. For example, a change involtage and/or current from the primary power supply can be detected,indicating a primary power supply compromise. In some examples, thechange in voltage from the primary power supply can fall outside of thepredetermined power threshold.

At 356, the process 350 can include not detecting a primary power supplycompromise. A primary power supply compromise is not detected if theloads connected to the node and/or change in voltage, current, etc.,changes, but the primary power supply is within the predetermined powerthreshold. In response to not detecting a primary power supplycompromise (e.g., the supply falls within a predetermined thresholdpower range), the process 350 can include continuing to monitor theprimary power supply, at 352.

Additionally and/or alternatively, in response to detecting a primarypower supply compromise, at 358, an early reset detection can betriggered. For example, the system firmware of the support switch and/orthe node may detect additional loads connected to the node and/or theearly reset. A reset can include clearing pending errors or events thatbring a system to a normal condition.

Based on the early reset detection and/or additional loads, a particularamount of power for a period of time may be available for the system.That is, the early reset detection can initiate a time threshold, at360, to prevent power cycling. The time threshold can be a particularperiod of time, available to the system, to initiate a self-refresh, asdiscussed further herein. The particular period of time can be used topreserve data entries, as further discussed herein.

At 362, a self-refresh can be performed. A self-refresh can includepreserving data entries prior to the primary power supply compromise.Preserving data entries refers to moving data entries prior to theprimary power supply compromise to non-volatile memory for retention.That is, the self-refresh can preserve each data entry among a pluralityof data entries, while additionally preventing new entries from beingentered and/or accepted by a central processing unit (CPU). That is,entries after the primary power supply compromise (e.g., new entries)may not be accepted by the CPU.

The CPU can be halted, such that only previous entries prior to theprimary power supply compromise are preserved. Each data entry can betransferred to the memory and/or preserved while the DIMMs (e.g., DIMM220 illustrated in FIG. 2) are in self-refresh. In some examples, thedata entries prior to the primary power supply compromise can includedestination targets which identify a location in system memory forretention. Destination targets, as used herein, are identifiersassociated with the data entries that can identify a particular locationand/or space within the system memory in which the data entry isassociated. For instance, a data entry that includes a destinationtarget may include an identifier associated with a portion of memory.

At 358, the early reset detection can also initiate a support switch, at364 (e.g., support switch 205 illustrated in FIG. 2). In some instances,the support switch can be initiated by a firmware update. An update canbe initiated by an update to the system firmware of the support switch.The support switch can enable and/or disable a hardware switch (e.g.,hardware switch 103, 203 illustrated in FIGS. 1 and 2) at 366. Thesupport switch can disable the hardware switch to prevent a circuitrymalfunction resulting from an unintended design flaw from sending anovercurrent, undercurrent, overvoltage, or undervoltage through thecircuit, which may cause damage to the MLB 228 (e.g., motherboard).

The support switch can disable the hardware switch from functioning andavoiding a power surge. In some examples, the support switch can alsoisolate the hardware switch from the shared backup power supply toprevent power transition. Isolation of the hardware switch by thesupport switch is preventing the hardware switch from accessing theshared backup power supply to power the node. Disabling the hardwareswitch can maintain the primary power supply to the node, but does notuse power from the backup power supply.

Further, in some examples, the support switch can enable the hardwareswitch to prepare for power transition. That is, the primary powersupply can be removed and/or severed, such that power from the primarypower supply ceases. The support switch can receive informationregarding load power requirements connected to the node. If the loadpower requirements exceed a predetermined power threshold, the supportswitch can enable the hardware switch to transition to the shared backuppower supply to provide additional power to the node. The support switchcan communicate with the hardware switch to prepare for powertransition.

At 368, the process 350 can include the support switch transitioning thenode via the hardware switch, to the shared backup power supply. Thatis, the hardware switch can receive communications from the supportswitch to transition the node from the primary power supply to theshared backup power supply. In some instances, the support switch canregulate the transition from the primary power supply to the sharedbackup power supply. The support switch can regulate the transition byconverting power so that a stable voltage/current and/or a predeterminedpower threshold (e.g., sufficient power level) can be provided to thenode. The regulated transition can prevent an unintended power surgefrom the shared backup power supply. In other words, the support switchcan regulate the power (e.g., voltage, current, etc.) supplied by theshared backup power supply.

At 370, the process 350 can include restoring saved data to systemmemory once the transition to the shared backup power supply iscomplete. For example, the data entries preserved from the self-refreshas previously discussed in relation to 362, can be restored andimplemented within the system. In some instances, upon the transitionfrom the primary power supply to the shared backup power supply, thedata can be implemented. For example, the shared backup power supply canpower the node and components such that the preserved data can beexecuted.

FIG. 4 illustrates a flow diagram of an example of a method 490 of powersupply support, according to the present disclosure. At 492, the method490 can include detecting a primary power supply compromise using asupport switch of a node, wherein the support switch includes systemfirmware. The system firmware of the support switch can receiveinformation related to the load power requirement connected to a node,and/or voltage/current of the primary power supply. Power changes (e.g.,loads, voltage/current changes) can indicate a primary power supplycompromise. Detection the primary power supply compromise can includerecognition of planned and/or unplanned primary power supply failures.In some instances, detection can be based on a predetermined powerthreshold. The predetermined power threshold can be selected by a userand/or automatically designated by the system.

At 494, the method 490 can include preventing data entries prior to theprimary power supply compromise from being entered into memory inresponse to detection of the primary power supply compromise. Dataentries received after the detection of a primary power supplycompromise may not be saved and/or preserved within non-volatile memory.Data entries converted prior to the primary power supply compromise canbe saved into memory, and data entries received after the primary powersupply compromise can be prevented from being entered while the nodetransitions to the shared backup power supply. Additionally, and/oralternatively, the data entries received prior to the detection of theprimary power supply compromise can be retained and/or preserved andsaved to non-volatile memory. Upon receipt of the shared backup power,the loads can implement the saved data entries within the node.

At 496, the method 490 can include transitioning the node to a sharedbackup power supply from the primary power supply, using the supportswitch, while the support switch enables a hardware switch. The supportswitch can enable and/or disable the hardware switch. Disabling thehardware switch is when transition to a shared backup power supply isnot instructed by the support switch and/or not functioning totransition. The hardware switch can maintain power to the node from theprimary power supply.

Enabling the hardware switch is the support switch communicating withthe hardware switch and instructing the hardware switch to transition toa shared backup power supply. The support switch can notify the hardwareswitch of a change in power requirements, such as a predetermined powerthreshold. For example, the loads connected to a node may change andadditional power may be needed to power the loads. The support switchcan communicate with the hardware switch to enable power transition fromthe primary power supply to the shared backup power supply. Enabling thehardware switch can include isolating the primary power supply from thenode to prepare for the transition. Isolating the primary power supplyis when power from the primary power supply ceased.

In some examples, the support switch can remain in an active mode untilthe transition from the primary power supply to shared backup powersupply is complete. As used herein, an active mode refers to the supportswitch enabling the hardware switch and transitioning the node to theshared backup power supply. That is, the active mode can include thesupport switch communicating with the hardware switch and/or regulatingthe shared backup power supply. Upon transitioning back to the primarypower supply from the shared backup power supply, the hardware switchcan be disabled and maintain power (e.g., voltage, current) from theprimary power supply to the node.

In the present disclosure, reference is made to the accompanyingdrawings that form a part hereof, and in which is shown by way ofillustration how a number of examples of the disclosure may be capableof being practiced. These examples are described in sufficient detail toenable those of ordinary skill in the art to practice the examples ofthis disclosure, and it is to be understood that other examples may becapable of being used and that process, electrical, and/or structuralchanges may be capable of being made without departing from the scope ofthe present disclosure.

The figures herein follow a numbering convention in which the firstdigit corresponds to the drawing figure number and the remaining digitsidentify an element or component in the drawing. Elements shown in thevarious figures herein may be capable of being added, exchanged, and/oreliminated so as to provide a number of additional examples of thepresent disclosure. In addition, the proportion and the relative scaleof the elements provided in the figures are intended to illustrate theexamples of the present disclosure, and should not be taken in alimiting sense.

As used herein, “logic” is an alternative or additional processingresource to perform a particular action and/or function, etc., describedherein, which includes hardware (e.g., various forms of transistorlogic, application specific integrated circuits (ASICs), etc.) asopposed to computer executable instructions (e.g., firmware, etc.)stored in memory and executable by a processor. Further, as used herein,“a” or “a number of” something can refer to one or more such things. Forexample, “a number of widgets” can refer to one or more widgets. Also,as used herein, “a plurality of” something can refer to more than one ofsuch things.

The above specification, examples and data provide a description of themethod and applications, and use of the system and method of the presentdisclosure. Since many examples may be capable of being made withoutdeparting from the spirit and scope of the system and method of thepresent disclosure, this specification merely sets forth some of themany possible example configurations and implementations.

What is claimed is:
 1. A backup power supply support system, comprising:a shared backup power supply controlled by a backup power controlmodule; and a support switch coupled to the shared backup power supply,wherein the support switch enables a transition from a primary powersupply to the shared backup power supply; a central processing unit(CPU) that is halted during the transition from the primary power supplyto the shared backup power supply; and wherein the support switchincludes system firmware to: detect a primary power supply compromise;isolate a dedicated hardware switch for each of a plurality of loadsfrom the shared backup power supply disable each dedicated hardwareswitch: maintain the primary power supply; enable each dedicatedhardware switch; disable the primary power supply; transition to theshared backup power supply; and disengage the primary power supply. 2.The system of claim 1, the support switch further comprising an earlyreset detection module, wherein the early reset detection moduleincludes a time threshold from which power from the primary power supplyis available.
 3. The system of claim 2, wherein the early resetdetection module initiates a self-refresh period.
 4. The system of claim1, further comprising a self-refresh period prior to the transition tothe shared backup power supply, wherein the self-refresh period retainsdata entries prior to the primary power supply compromise.
 5. The systemof claim 1, wherein the support switch detects an unplanned primarypower supply compromise and initiates a power transition to the sharedbackup power supply.
 6. The system of claim 1, further comprising thesystem firmware of a support switch to determine adequate power currentto a node from the shared backup power supply.
 7. A non-transitorymachine readable medium storing instructions executable by a processingresource to cause a computer to: detect a primary power supplycompromise associated with a node using a support switch, wherein thesupport switch includes system firmware; convert data entries receivedprior to the primary power supply compromise into memory; and preventdata entries received after the primary power supply compromise frombeing entered; transition the node from the primary power supply to ashared backup power supply using the support switch, wherein the supportswitch: isolates a dedicated hardware switch for each of a plurality ofloads from the shared backup power supply; disables each dedicatedhardware switch; maintains the primary power supply; enables eachdedicated hardware switch; disables the primary power supply: andverifies adequate power current to the node from the shared backup powersupply.
 8. The medium of claim 7, including instructions executable bythe processing resource to initiate a self-refresh period to retain dataentries received prior to the primary power supply compromise by movingthe data entries to non-volatile memory.
 9. The medium of claim 7,including instructions to isolate the primary power supply from the nodeto prepare for the transition.
 10. A method of backup power supplysupport, comprising: detecting a primary power supply compromise using asupport switch of a node, wherein the support switch includes systemfirmware to isolate a dedicated hardware switch for each of a pluralityof loads from a shared backup power supply by disabling each dedicatedhardware switch to maintain the primary power supply and to enable eachdedicated hardware switch to disable the primary power supply;converting data entries received prior to the primary power supplycompromise into memory; and preventing data entries prior to the primarypower supply compromise from being entered into memory in response todetection of the primary power supply compromise; and transitioning thenode to the shared backup power supply from the primary power supply,using the support switch, while the support switch enables eachdedicated hardware switch.
 11. The method of claim 10, comprisingactivating a self-refresh period prior to the transition to the sharedbackup power supply, wherein the self-refresh period moves data entriesprior to the primary power supply compromise to non-volatile memory forretention.
 12. The method of claim 10, comprising retaining the supportswitch in an active mode until the transition from the primary powersupply to the shared backup power supply is complete.
 13. The method ofclaim 10, comprising restoring saved data to system memory after thetransition to the shared backup power supply is complete.
 14. The methodof claim 10, wherein the data entries prior to the primary power supplycompromise include destination targets which identify a location insystem memory for retention.
 15. The backup power supply support systemof claim 1, wherein each of the dedicated hardware switches is embeddedin the plurality of loads.
 16. The backup power supply support system ofclaim 1, further comprising a Baseboard Management Controller (BMC) unitthat enables communication between the shared backup power supply andthe plurality of loads.
 17. The backup power supply support system ofclaim 1, wherein the support switch can regulate the transition from theprimary power supply to the shared backup power supply.
 18. The backuppower supply support system of claim 1, wherein at least one of thededicated hardware switches is a transformer.